fix pipelunerun provenance when multiple tasks have the same name (ca… #1169
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…se of use of matrix to fan out tasks on a pipeline)
Changes
Chains only generates provenance attestations for the first image in a matrix of TaskRuns, while all images are signed. The issue is rooted in the assumption that PipelineTaskRuns have unique names within a Pipeline, which isn't true when a matrix is used. The PR aims to address this by ensuring that provenance attestations are generated for all images in the matrix.
fixes #1164
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
functionality, content, code)
Release Notes